Ourdomain name is 18 digits long.I cannot ping our short "NetBios" name or join with it. I can add the same laptop to the domain with Vista x64. However with Windows 7 I see the same problem. Hope someone can help...Thanks,Michael - Asst. Desktop Manager

Do you get the same issue as I get (see other post).Look in %windir%\debug\netsetup.loglook for *=, you may see your FQDN getting snippend.I think its passing thewrong param to an API.steve

Yes, same truncation it looks like:01/09/2009 07:30:54:901 DomainDnsPolicy:01/09/2009 07:30:54:901 Name: teleperformanceu=*)01/09/2009 07:30:54:901 DnsDomainName: teleperformanceusa.com01/09/2009 07:30:54:901 DnsForestName: teleperformanceusa.com01/09/2009 07:30:54:901 DomainGuid: 5407c8ce-584e-4fd5-8548-911f4719e43601/09/2009 07:30:54:901 Sid: S-1-5-21-3837813750-218278948-1069949287Michael - Asst. Desktop Manager

I am connecting to a Windows 2003 R2 Domain.Michael - Asst. Desktop Manager

Hi,Yes, this is a known issue within Build 7000 for both Windows 7 client and Windows Server 2008 R2. You will have this issue if the *leading* name portion of your fully qualified domain name is more than 15 characters.Examples: northwindtraders.com <-- will give parameter is incorrect.contoso.fabrikam.treyresearch.net <-- will work fine.There will be a hotfix released in the near future. If you are part of any of the private beta programs, you already have access to this through https://connect.microsoft.com.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Do you have a hotfix number or anything I can reference on MSDN?Thank you for your help!Michael - Asst. Desktop Manager

thank god its not only me, this has been driving me crazy all morning....so there is no way around it until the update is relaesed?

Correct, the only workaround would be to rename the domain or build a new domain - obviously not valid workarounds. :) As a side point, this should be listed in the release notes for the Beta. Please make sure to review those notes for any other known issues.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Yes, I did read the release notes before installing and just re-read them. I see nothing of this sort in them with regards to this issue, but maybe I'm missing something.Michael - Asst. Desktop Manager

No, you didn't miss anything - this failed to make it into the notes after all. We're working on getting a KB article out ASAP, along with the fix. Thanks for hanging tight, it might be a couple of days.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Does this affect samba domains, too? If I try to join my domain at home, I get "The specified domain either does not exist or could not be contacted.", though my other computers (running Vista and XP) have no problems joining.

Only if your SAMBA DNS domain name was meeting the rules above. That error you are getting is something else though, and appears to be purely network related. Can you ping your SAMBA DC's, browse them, etc? Are they on the same subnet as your Win7 client, and is that Win7 client on the same subnet as the working computers. Firewall on/off? Could be quite a few things, almost all of them environmental.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

I only have 1 DC, and I can browse it if I enter it's name directly (that is Win+R -> \\deepthought - I don't see it if I browse the network, only my Vista machine and printer appear there; it asks me for credentials, and I can then access the shares on it normally). I have also tried disabling the Windows firewall, but it had no effect.If I try joining the domain, I'm asked for the username and password, and after entering them, I get the error. I can see from the logs that there is some communication between Windows and Samba, but joining ultimately fails.01/11/200920:14:58:569----------------------------------------------------------------- 01/11/200920:14:58:616NetpValidateName:checkingtoseeif'WIN7VM'isvalidastype1name 01/11/200920:14:58:616NetpCheckNetBiosNameNotInUsefor'WIN7VM'[MACHINE]returned0x0 01/11/200920:14:58:616NetpValidateName:name'WIN7VM'isvalidfortype1 01/11/200920:14:58:616----------------------------------------------------------------- 01/11/200920:14:58:616NetpValidateName:checkingtoseeif'win7vm'isvalidastype5name 01/11/200920:14:58:616NetpValidateName:name'win7vm'isvalidfortype5 01/11/200920:14:58:616----------------------------------------------------------------- 01/11/200920:14:58:616NetpValidateName:checkingtoseeif'yggdrasil'isvalidastype3name 01/11/200920:14:58:632NetpCheckDomainNameIsValid[Exists]for'yggdrasil'returned0x0 01/11/200920:14:58:632NetpValidateName:name'yggdrasil'isvalidfortype3 01/11/200920:15:02:429----------------------------------------------------------------- 01/11/200920:15:02:429NetpDoDomainJoin 01/11/200920:15:02:429NetpMachineValidToJoin:'WIN7VM' 01/11/200920:15:02:429OSVersion:6.1 01/11/200920:15:02:429Buildnumber:7000(7000.winmain_win7beta.081212-1400) 01/11/200920:15:02:429SKU:Windows7Ultimate 01/11/200920:15:02:429NetpDomainJoinLicensingCheck:ulLicenseValue=1,Status:0x0 01/11/200920:15:02:429NetpGetLsaPrimaryDomain:status:0x0 01/11/200920:15:02:429NetpMachineValidToJoin:status:0x0 01/11/200920:15:02:429NetpJoinDomain 01/11/200920:15:02:429Machine:WIN7VM 01/11/200920:15:02:429Domain:yggdrasil 01/11/200920:15:02:429MachineAccountOU:(NULL) 01/11/200920:15:02:429Account:yggdrasil\ender 01/11/200920:15:02:429Options:0x25 01/11/200920:15:02:429NetpValidateName:checkingtoseeif'yggdrasil'isvalidastype3name 01/11/200920:15:02:429NetpCheckDomainNameIsValid[Exists]for'yggdrasil'returned0x0 01/11/200920:15:02:429NetpValidateName:name'yggdrasil'isvalidfortype3 01/11/200920:15:02:429NetpDsGetDcName:tryingtofindDCindomain'yggdrasil',flags:0x40001010 01/11/200920:15:09:944NetpDsGetDcName:failedtofindaDCinthespecifieddomain:0x54b,lasterroris0x0 01/11/200920:15:09:944NetpJoinDomainOnDs:NetpDsGetDcNamereturned:0x54b 01/11/200920:15:09:944NetpJoinDomainOnDs:Functionexitswithstatusof:0x54b 01/11/200920:15:09:944NetpDoDomainJoin:status:0x54b 01/11/200920:15:09:944----------------------------------------------------------------- 01/11/200920:15:09:944NetpDoDomainJoin 01/11/200920:15:09:944NetpMachineValidToJoin:'WIN7VM' 01/11/200920:15:09:944OSVersion:6.1 01/11/200920:15:09:944Buildnumber:7000(7000.winmain_win7beta.081212-1400) 01/11/200920:15:09:944SKU:Windows7Ultimate 01/11/200920:15:09:944NetpDomainJoinLicensingCheck:ulLicenseValue=1,Status:0x0 01/11/200920:15:09:944NetpGetLsaPrimaryDomain:status:0x0 01/11/200920:15:09:944NetpMachineValidToJoin:status:0x0 01/11/200920:15:09:944NetpJoinDomain 01/11/200920:15:09:944Machine:WIN7VM 01/11/200920:15:09:944Domain:yggdrasil 01/11/200920:15:09:944MachineAccountOU:(NULL) 01/11/200920:15:09:944Account:yggdrasil\ender 01/11/200920:15:09:944Options:0x27 01/11/200920:15:09:944NetpValidateName:checkingtoseeif'yggdrasil'isvalidastype3name 01/11/200920:15:10:054NetpCheckDomainNameIsValid[Exists]for'yggdrasil'returned0x0 01/11/200920:15:10:054NetpValidateName:name'yggdrasil'isvalidfortype3 01/11/200920:15:10:054NetpDsGetDcName:tryingtofindDCindomain'yggdrasil',flags:0x40001010 01/11/200920:15:10:054NetpDsGetDcName:failedtofindaDCinthespecifieddomain:0x54b,lasterroris0x0 01/11/200920:15:10:054NetpJoinDomainOnDs:NetpDsGetDcNamereturned:0x54b 01/11/200920:15:10:054NetpJoinDomainOnDs:Functionexitswithstatusof:0x54b 01/11/200920:15:10:054NetpDoDomainJoin:status:0x54b

You will need a double-sided network trace to see what's happening here Ender9. The error only highlights what we already know, that there is a network problem. It's the DCLOCATOR process that's failing here, so it appears to be name resolution that's not working. I don't have a way to test this though, as I do not run SAMBA. You may also want to give them a shout to see if they have run into any issues with default Win7 in this Beta build or with the PDC M3 exit build.So - network capture util on both servers (netmon 3.2 or Wireshark on the Win7, whatever you like on the Samba). Make sure you flush DNS and NETBIOS caches on the client (ipconfig /flushdns and nbtstat -R), then start both captures. Try to join, get error, stop captures, examine captures.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

I tried a capture and then compared it with a capture from Windows 2000 machine. It appears that Windows 7 gives up very fast - there were 31 packets captured compared to 254 from the 2k machine. I have uploaded the captures here.

has this fix been released or posted anywhere yet? if not any idea when it will be coming?

So do we have an ETA on this fix? If it's already done, why is it not accessible? I'd love to test win7 out, but unfortunately can't if I can't get it onto my domain, and I cannot find ANYTHING on the connect site.

The fix was being tested. We hope to have it out for you very soon.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Thanks, Ned.So how soon is soon? Any chance I can help test it? I'm just ITCHIN' for some win7 action. From what I've seen of it's responsiveness with casual web browsing, (mostly forums to find this fix) I'd love to give it a shot, and see how it handles my day-to-day.Thanks again.

Hi Everyone,The hotfix is now available to download for allcustomers having this issue. The KB article will be following soon, butwe thought you want this ASAP:Download QFE KB961402 "- http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=961402&kbln=en-us There are three versions of the file, for x86, X64, and IA64. It is language neutral It is for Windows 7 and Windows Server 2008 R2 (OS agnostic) When you follow this link, it will email you a location to a download of the file(s). This hotfix should only be applied if you are experiencing the following: SYMPTOMS Under the following circumstances, you may receive an error The attempt to join this computer to the contoso.com domain failed. The parameter is incorrect: You attempt to join a Windows 7 or Windows Server 2008 R2 computer to an existing domain using the System Properties UI or with NETDOM JOIN. You attempt to DCPROMO a Windows Server 2008 R2 computer to an existing domain. The NETSETUP log on the computer being joined (located in %systemroot\debug) will also show: 12/23/2008 16:06:19:419 NetpSetLsaPrimaryDomain: for 'northwindtraders' status: 0xc000000d 12/23/2008 16:06:19:419 NetpJoinDomainLocal: status of setting LSA pri. domain: 0x57 12/23/2008 16:06:19:419 NetpJoinDomainLocal: initiating a rollback due to earlier errors 12/23/2008 16:06:19:419 NetpLsaOpenSecret: status: 0x0 12/23/2008 16:06:19:419 NetpJoinDomainLocal: rollback: status of deleting secret: 0x0 12/23/2008 16:06:19:419 NetpClearFullJoinState: Removing cached state from the registry... 12/23/2008 16:06:19:419 NetpClearFullJoinState: Status of deleting join state key 0x0 12/23/2008 16:06:19:419 NetpMarkLastFullJoinAttempt: No offline domain join information found, FinishJoin key not found. 12/23/2008 16:06:19:419 NetpCompleteOfflineDomainJoin: An error occured while completing the offline join action, the action can be tried again. The error code was: 0x57. 12/23/2008 16:06:19:419 NetpCompleteOfflineDomainJoin: status: 0x57 12/23/2008 16:06:19:419 NetpDoDomainJoin: status: 0x57 Note: 0x57 translates to ERROR_INVALID_PARAMETER. The domain does not need to be named NORTHWINDTRADERS.COM for this issue to occur. Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Hi Ned,Thanks for posting back here with that update. Appreciate the help you give in the forums (especially the DFSR stuff!)Mat Mirabito [MCITP, MCSE]

:(I can only find the x86 version on that link you posted.Mat Mirabito [MCITP, MCSE]

Great Thanks so much..I found the x64 version (The explorer redirects automat to the right link)Tested and it works fine on my x64 based whit a 22 length domain name.Thanks.

Thanks for the link! All I see, however, is an x86 version of the file - not x64 (as I need) or IA64.Wait - nevermind. With a 32-bit browser, you must select "Show hotfixes for all platforms and all languages (3)."

Putting this to bed: You cannot join a Windows 7 Beta-based or a Windows Server 2008 R2 Beta-based computer to an existing domain, and you receive an error message: "The parameter is incorrect" - http://support.microsoft.com/kb/961402Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team

Great service guys!Whoops, a bit premature with the praise.It worked a treat on a W7 box, but I'm trying the same trick on an AMD box with W2008 R2 and the bloody hotfix won't install - "wrong version". I've tried the Itanium and the other 64 bit one, no luck.Any ideas anyone? Any manual fixes? (I'm going to shoot the guy who invented a long domain name for us.)By the way: Windows Seven is absolutely awesome. Mucho congratulations, guys. Building software myself I know it's a tough gig - to do something on this scale so well: brilliant, almost unbelievable. There once was a theory that if something took more than ten man-years it couldn't be built. You've blown that one out of the water.

need fix to join windows 7 box to samba domain............any word on a fix for this????

Hotfix is at the top of the page that Ned Pyle gave:http://support.microsoft.com/kb/961402. They send it to you via email since it's not publicly supported yet.Owner, Quilnet Solutions

I am having trouble joining a Windows 7 PC to our SBS 2003R2 domain. Do not know whether this is the same network issue, and whether the hotfix referred to earlier will fix this problem? The 'join domain' wizard fails and says there is a 'networking problem'.Our domain is XXXXXXXXXXXXXX.lan - so the first segment is 14 characters long, and in total its 18 characters.Any help would be appreciated!

It sounds like adifferent issue. Please start a new thread with the exact error you are getting. Also, go into the %systemroot%\debug folder, rename the netsetup.log, reproduce the error, then paste the contents of that log.Ned Pyle [MSFT] - MS Enterprise Platforms Support - Beta Team